Diagnosing Dashboard Performance Problems in Tableau

Diagnosing dashboard performance problems in Tableau is an essential skill for data analysts, business intelligence developers, and Tableau professionals. A dashboard may become slow because of complex calculations, large datasets, inefficient data connections, excessive filters, too many worksheets, high numbers of marks, or poorly optimized visualizations. Effective diagnosis involves identifying the source of the delay, analyzing performance recordings, testing individual worksheets, optimizing queries, and improving dashboard design.

The objective is not simply to make a dashboard load faster. It is to ensure that users can interact with reliable data, apply filters efficiently, explore business insights, and make decisions without unnecessary waiting.

Explore Tableau Training: JustAcademy Tableau Training

Course Demo: Register for a Tableau Course Demo

1. Learning Objectives

After completing this topic, learners will be able to:

• Understand dashboard performance and its importance.
• Identify common causes of slow Tableau dashboards.
• Use Tableau Performance Recording to diagnose bottlenecks.
• Analyze query execution, query compilation, and rendering delays.
• Identify inefficient worksheets, calculations, filters, and dashboard actions.
• Understand the difference between data source problems and visualization problems.
• Improve performance using extracts, efficient data models, and optimized calculations.
• Reduce unnecessary marks, worksheets, filters, and dashboard objects.
• Compare performance in Tableau Desktop and Tableau Server or Tableau Cloud.
• Apply a systematic troubleshooting workflow to a real-world dashboard.

2. What Is Dashboard Performance in Tableau?

Dashboard performance refers to how quickly and efficiently a Tableau dashboard loads, displays visualizations, processes user interactions, and updates results when users change filters or selections.

A high-performing dashboard allows users to open reports, explore data, and interact with visualizations without excessive delays.

Important Performance Measurements

Important: A dashboard can be slow for several different reasons. Measuring the delay before making changes helps identify the actual cause instead of relying on guesswork.

3. Why Dashboard Performance Matters

Dashboard performance affects the usability, adoption, and effectiveness of business intelligence solutions.

• Better user experience: Users can explore data without unnecessary waiting.
• Faster decision-making: Business users can access important metrics quickly.
• Improved productivity: Analysts spend less time waiting for reports to refresh.
• Better scalability: Efficient workbooks are easier to maintain as data volumes increase.
• Lower resource consumption: Efficient queries and calculations can reduce unnecessary processing.
• Greater dashboard adoption: Responsive dashboards encourage regular use.

4. Common Causes of Slow Tableau Dashboards

Before optimizing a dashboard, identify which layer is responsible for the performance problem.

5. Understanding the Dashboard Performance Diagnosis Process

A systematic diagnosis process helps isolate the source of a delay before changing the workbook.

Step 1: Reproduce the Problem

Open the dashboard and repeat the action that causes the delay. Examples include opening the dashboard, changing a filter, selecting a mark, or switching between views.

Step 2: Measure the Delay

Record the approximate time taken for the action to complete. Compare the result with previous behavior or an agreed performance target.

Step 3: Identify the Slow Component

Determine whether the delay comes from data retrieval, query compilation, calculations, layout processing, rendering, or server infrastructure.

Step 4: Inspect Performance Recording

Use Tableau Performance Recording to identify time-consuming events and investigate the relevant worksheets or queries.

Step 5: Make One Change at a Time

Modify one component, such as a filter, calculation, data connection, or worksheet. Retest the dashboard to determine whether the change improved performance.

Step 6: Validate Accuracy

Ensure that optimization has not changed the meaning of business metrics, removed required records, or introduced calculation errors.

Step 7: Test the Published Dashboard

Validate the workbook in its intended deployment environment, because browser behavior, network latency, data source access, and server workload may affect performance.

6. Using Tableau Performance Recording

Tableau Performance Recording is one of the most useful tools for identifying dashboard bottlenecks. It records information about selected workbook events and presents the results in a performance analysis workbook.

Depending on the environment and version, recorded events can include query execution, query compilation, data source connections, layout computations, extract generation, geocoding, data blending, and server rendering.

How to Start Performance Recording in Tableau Desktop

1. Open the workbook in Tableau Desktop.
2. Open the Help menu.
3. Select Settings and Performance.
4. Choose Start Performance Recording.
5. Open the dashboard and reproduce the slow action.
6. Change the relevant filters or interact with the views you want to test.
7. Return to Help > Settings and Performance.
8. Select Stop Performance Recording.
9. Inspect the generated performance workbook.

What to Examine

• Which events take the longest?
• Which dashboard or worksheet is associated with those events?
• Are queries slow, or are many queries being executed?
• Is query compilation taking a long time?
• Does layout computation or rendering dominate the delay?
• Does the delay occur during initial loading or after a user interaction?

Important: Performance Recording identifies where time is spent; it does not automatically fix the underlying problem. Interpret the results and test targeted improvements.

7. Understanding the Performance Recording Dashboard

The generated performance workbook includes summary information and more detailed views that help developers investigate slow operations.

How to Interpret Long Events

• Long query execution: Investigate the database, query complexity, data volume, and connection type.
• Long query compilation: Review complex calculations, numerous filters, and workbook complexity.
• Long layout computation: Simplify dashboard and worksheet layout.
• Long connection time: Investigate network latency, authentication, and data source availability.
• Long rendering time: Reduce marks and unnecessary visual detail.
• Long extract generation: Review extract size, included fields, and refresh design.

For some published data source connections and newer Tableau versions, recorded query events may be represented differently from traditional direct database connections. Interpret the event names according to the environment being tested.

8. Diagnosing Slow Query Execution

Query execution is the time required to retrieve or process data through the underlying data source. Slow query execution may occur because of large datasets, complex joins, inefficient database logic, missing indexes where relevant, high database workload, or network latency.

Common Symptoms

• A worksheet takes a long time to display its data.
• Several dashboard charts wait for queries to finish.
• Filtering a view triggers slow database requests.
• The same source query is slow outside Tableau.

Diagnosis Steps

1. Identify the query event in the Performance Recording workbook.
2. Determine which worksheet or interaction triggered it.
3. Inspect the available query text and relevant source information.
4. Run or analyze the query using the database's approved diagnostic tools, if permitted.
5. Ask the database team to review execution plans and indexing where appropriate.
6. Reduce unnecessary fields and records when possible.
7. Test whether an extract would be appropriate for the freshness and data-volume requirements.

Example

A sales dashboard connects to a database containing millions of transaction records. Opening the dashboard requires several detailed queries, causing a long delay.

Possible improvements include filtering the source to relevant dates, using an appropriately designed extract, aggregating data to the required level, or optimizing the source query.

Important: Do not remove required data simply to make the dashboard faster. The chosen optimization must preserve the business purpose of the report.

9. Diagnosing Slow Query Compilation

Query compilation refers to the work Tableau performs to generate or compile queries needed for a visualization. Compilation may take longer when a workbook contains complex calculations, numerous filters, nested expressions, or complicated view definitions.

Possible Causes

• Many calculated fields used in the same view.
• Nested IF statements or complex string operations.
• Complicated level of detail expressions.
• Excessive filtering logic.
• Complex custom SQL or data model definitions.
• Large and complicated workbook structures.

How to Troubleshoot

1. Locate the query compilation events in Performance Recording.
2. Identify the worksheets associated with the slow events.
3. Review calculated fields used by those worksheets.
4. Remove unused calculations and simplify unnecessary logic.
5. Evaluate whether some calculations can be performed efficiently in the underlying data source.
6. Retest after each meaningful change.

Example: Simplifying a Calculation

Suppose a workbook contains a lengthy calculation that repeatedly checks the same condition. Where the logic permits, create a reusable calculated field for the repeated condition and simplify the dependent calculations.

// Example: reusable category classification
IF [Sales] >= 10000 THEN
    "High Sales"
ELSE
    "Standard Sales"
END

This example illustrates a simple classification field. It does not guarantee a performance improvement in every workbook; measure the result using Performance Recording.

10. Diagnosing Excessive Worksheet and Dashboard Complexity

A dashboard containing too many worksheets, charts, filters, legends, images, and layout containers may require additional queries and rendering work. Displaying many visualizations simultaneously can also make the dashboard difficult to understand.

Common Problems

• Too many charts displayed on one screen.
• Multiple worksheets showing nearly identical information.
• Large tables with thousands of rows.
• Excessive legends and filter cards.
• Unnecessary decorative elements and layout containers.
• Charts that contain much more detail than users need.

Resolution Steps

1. List the worksheets used by the dashboard.
2. Identify views that do not contribute to the main business questions.
3. Remove redundant charts and unnecessary objects.
4. Replace excessive detail with summaries and drill-down views.
5. Move secondary analysis to a separate dashboard when appropriate.
6. Test the load time and usability after simplifying the layout.

Example

An executive dashboard contains 15 charts, several large tables, and many filter cards. Instead of displaying everything at once, the developer keeps the most important KPIs and trends on the main dashboard and moves detailed analysis to supporting views.

This approach can reduce the initial workload and make the dashboard easier to navigate.

11. Diagnosing Too Many Marks in a Visualization

A mark is a visual representation of data in Tableau, such as a bar, point, line, square, or geographic symbol. A worksheet with too many marks can increase rendering and interaction costs.

Common Causes

• Displaying individual records instead of aggregated values.
• Adding many dimensions to the Marks card.
• Using detailed geographic maps with many locations.
• Showing a very large number of labels.
• Displaying excessive detail in a scatter plot or text table.

How to Reduce Mark Count

1. Identify the level of detail required for the analysis.
2. Remove dimensions that are not necessary for the visualization.
3. Aggregate measures at a useful business level.
4. Filter out irrelevant records where appropriate.
5. Use summaries and drill-down actions for detailed analysis.
6. Remove unnecessary labels and visual encodings.

Example

Instead of plotting every sales transaction on a chart, display total sales by month and region. Users can then select a month or region to explore more detailed records.

Best practice: Reduce unnecessary detail without removing information users need to make decisions.

12. Diagnosing Filter-Related Performance Problems

Filters make dashboards interactive, but excessive or poorly designed filter controls can increase query workload and complicate workbook behavior.

Common Filter Problems

• Many quick filters are visible at the same time.
• A filter contains thousands of possible values.
• Changing a filter triggers many queries across the dashboard.
• Users select multiple values one at a time, causing repeated updates.
• Complex filter logic makes queries expensive.

Recommended Solutions

• Keep only essential filter controls visible.
• Use guided analysis rather than exposing every possible filter.
• Evaluate the Show Apply Button option for filters that support it, so multiple selections can be applied together.
• Consider dashboard filter actions when they provide a simpler interaction.
• Use extract and data source filters when reducing the available data is appropriate.
• Test context filters only when their behavior or measured performance justifies them.

Example

A dashboard has filters for country, state, city, customer, product, order ID, and date. Many of these controls may be unnecessary for the main task. Keep the high-value filters visible and provide more detailed exploration through drill-down or separate worksheets.

Always verify the behavior of filter actions and filter scope after making changes.

13. Diagnosing Slow Calculated Fields

Calculated fields allow Tableau developers to create custom business logic. However, complicated or repeated calculations can contribute to slow query compilation, query execution, or rendering.

Potentially Expensive Patterns

• Repeated complex string operations on large datasets.
• Deeply nested conditional expressions.
• Many calculations that depend on other calculations.
• Complex LOD expressions used in many worksheets.
• Calculations applied to large numbers of marks.

Optimization Techniques

1. Identify calculations used by slow worksheets.
2. Remove unused calculated fields from the workbook when safe to do so.
3. Simplify repeated or unnecessarily complicated logic.
4. Use native Tableau functionality such as groups, sets, bins, or date fields when it suits the requirement.
5. Consider moving suitable transformations into a database view or prepared data source.
6. Test the impact on both performance and numerical accuracy.

Example: Sales Category

IF [Sales] >= 50000 THEN
    "High"
ELSEIF [Sales] >= 20000 THEN
    "Medium"
ELSE
    "Low"
END

This calculation classifies sales into three categories. Whether it should be computed in Tableau or upstream depends on the source, workbook design, reuse, and performance evidence.

14. Diagnosing Slow Data Connections

A dashboard may be slow because Tableau takes a long time to connect to its data source. Connection delays can arise from network latency, database workload, authentication, connectivity configuration, or the availability of the source system.

Common Symptoms

• The dashboard pauses before retrieving data.
• Several worksheets experience similar delays.
• The same data source is slow across different workbooks.
• Performance changes depending on network conditions.

Troubleshooting Steps

1. Check whether the delay occurs while connecting or after queries begin.
2. Test the source connection using approved database tools.
3. Confirm that the database and network are available.
4. Check authentication and connection configuration.
5. Coordinate with the database or infrastructure team if necessary.
6. Compare the behavior of the dashboard in Desktop and the published environment.

Optimizing the workbook alone will not solve every connection problem. Some issues must be resolved at the network, database, or server level.

15. Live Connections Versus Extracts

Tableau can use live connections or extracts. The appropriate choice depends on data freshness requirements, data volume, source performance, refresh schedules, and operational needs.

How to Decide

1. Measure the current dashboard's performance.
2. Identify whether the source query is the main bottleneck.
3. Determine how current the data must be.
4. Estimate extract size and refresh requirements.
5. Test an extract when appropriate.
6. Compare query speed, refresh time, and data freshness before making a decision.

Important: Extracts are not guaranteed to be faster in every situation. The correct choice should be based on testing and business requirements.

16. Diagnosing Data Model and Join Problems

Incorrect or inefficient data modeling can cause slow queries, unexpectedly large result sets, and inaccurate metrics. Joins and relationships should match the intended grain of the source tables.

Common Issues

• Joining tables using incomplete keys.
• Combining tables with different levels of detail.
• Creating unnecessarily complex join structures.
• Using custom SQL that produces a large or inefficient result set.
• Duplicating measure values after a one-to-many join.

Resolution Steps

1. Document the grain of each table.
2. Check join keys and relationship configuration.
3. Compare record counts and totals before and after combining tables.
4. Review whether the data model returns only the fields and rows needed.
5. Ask the database team to review expensive queries where necessary.
6. Validate both performance and business metrics after making changes.

Never optimize a dashboard by removing records or changing joins without confirming that the resulting metrics remain correct.

17. Diagnosing Slow Dashboard Rendering

Rendering is the process of drawing visual elements and arranging dashboard components on the screen. A dashboard may retrieve data quickly but still take time to display its visualizations.

Common Causes

• Large numbers of marks.
• Many labels and annotations.
• Complex geographic visualizations.
• Numerous dashboard objects.
• Complicated nested containers.
• Excessive detail in tables and charts.

How to Improve Rendering

• Reduce unnecessary marks and labels.
• Remove decorative objects that do not support the analysis.
• Simplify maps and high-detail charts.
• Use concise summaries and drill-down views.
• Reduce unnecessary worksheet duplication.
• Test the dashboard at the actual display size used by its audience.

If Performance Recording indicates that layout or rendering events dominate, focus on workbook design instead of assuming that the database is the problem.

18. Diagnosing Dashboard Action Problems

Dashboard actions allow users to filter, highlight, navigate, or change views through interactions. Too many actions or actions that trigger expensive updates may contribute to slow interactions.

Common Problems

• A click updates several worksheets unnecessarily.
• A filter action passes a large set of values.
• Multiple actions trigger overlapping queries.
• Clearing a selection causes unexpected updates.
• Several worksheets repeat similar calculations after an action.

How to Troubleshoot

1. Open the dashboard's Actions settings.
2. List the actions and their source and target worksheets.
3. Identify actions that are redundant or no longer needed.
4. Reduce the number of target worksheets where appropriate.
5. Test the action using representative selections.
6. Use Performance Recording to measure the interaction before and after changes.

19. Diagnosing Tableau Server and Tableau Cloud Performance

A workbook that performs well in Tableau Desktop may behave differently after publishing. The published environment introduces additional factors such as server capacity, concurrent users, authentication, network latency, permissions, and shared data source workloads.

Potential Causes

• High concurrent user activity.
• Insufficient server resources for the workload.
• Slow data source access from the server environment.
• Extract refresh jobs competing with interactive requests.
• Network latency between the server and data source.
• Differences in browser rendering or published workbook configuration.

Resolution Steps

1. Confirm whether the problem occurs only after publishing.
2. Compare the same dashboard and interaction in Desktop and the published environment.
3. Use available server-side performance recording and monitoring tools.
4. Check extract refresh schedules and concurrent workloads.
5. Review permissions, authentication, and data source connectivity.
6. Involve the Tableau administrator or infrastructure team for server-level issues.

Publishing a workbook does not automatically optimize its design. Workbook tuning, data source tuning, and environment monitoring may all be necessary.

20. Using Workbook Optimizer

Tableau Workbook Optimizer can evaluate workbook design choices against performance best practices and provide recommendations. Availability and interface details depend on the Tableau product and version.

General Workflow

1. Open the workbook or published dashboard in an environment that supports Workbook Optimizer.
2. Open the relevant publishing or editing menu.
3. Run Workbook Optimizer if the option is available.
4. Review the recommendations.
5. Prioritize recommendations that match the measured bottleneck.
6. Apply appropriate changes and test the results.

Workbook Optimizer is a useful starting point, but it does not replace performance measurement. A recommendation should be evaluated against the workbook's actual data, user needs, and performance evidence.

21. Practical Project: Diagnose a Slow Sales Dashboard

Project Objective

Create a sales dashboard and practice diagnosing common performance problems involving queries, filters, calculations, and visualization design.

Sample Dataset

Task 1: Connect to the Dataset

1. Open Tableau Desktop.
2. Connect to the dataset using the appropriate connector.
3. Verify that Order ID, Region, Category, Sales, and Profit have the correct data types.
4. Confirm the number of records and validate the source data.

Task 2: Create Core Worksheets

• Create a KPI for total sales using SUM([Sales]).
• Create a profit KPI using SUM([Profit]).
• Create a bar chart showing sales by region.
• Create a chart showing sales by category.
• Create a trend chart if a valid date field is available.

Task 3: Build the Dashboard

1. Place the KPI cards at the top.
2. Add sales by region and sales by category.
3. Add only the filters required by the business question.
4. Configure filter actions where appropriate.
5. Remove unnecessary objects and duplicate charts.

Task 4: Record Baseline Performance

1. Open Performance Recording.
2. Load the dashboard and interact with its filters.
3. Stop the recording.
4. Note the longest-running events.
5. Record which worksheets or interactions are associated with those events.

Task 5: Diagnose the Bottleneck

Use the performance recording to determine whether the main delay is related to query execution, query compilation, data source connection, layout, or rendering.

Task 6: Optimize the Dashboard

• Remove unnecessary worksheets.
• Reduce excessive marks and labels.
• Simplify calculations where appropriate.
• Reduce unnecessary filter controls.
• Investigate the source query if execution is slow.
• Evaluate an extract if appropriate for the data freshness requirements.

Task 7: Measure Again

Repeat the same actions under comparable conditions and compare the results with the baseline. Confirm that the dashboard remains accurate and that the optimization has improved the intended interaction.

Project Deliverables

• A completed Tableau sales dashboard.
• A baseline performance recording.
• A list of identified bottlenecks.
• A record of changes made and why they were selected.
• A before-and-after performance comparison.
• A validation checklist confirming that the metrics remain correct.

22. Performance Troubleshooting Decision Table

23. Best Practices for Dashboard Performance

• Start with measurement: Use Performance Recording before changing workbook design.
• Keep dashboards focused: Display only visualizations that support the primary business questions.
• Reduce unnecessary marks: Use the appropriate level of detail for each chart.
• Limit filters: Provide the filters users actually need.
• Optimize data sources: Retrieve only the data required for analysis.
• Use extracts appropriately: Consider extracts when their refresh and freshness characteristics match business requirements.
• Simplify calculations: Remove redundant or unnecessarily complex logic.
• Review the data model: Ensure that relationships and joins match the intended data grain.
• Test dashboard actions: Avoid interactions that trigger unnecessary work.
• Use realistic test data: Performance with a small sample may not represent production behavior.
• Validate the published version: Test the actual environment where users access the dashboard.
• Document changes: Record the original issue, the change, and the measured outcome.

24. Common Mistakes to Avoid

25. Interview Questions and Answers

Q1. What is dashboard performance in Tableau?

Answer: Dashboard performance describes how quickly and efficiently a dashboard loads, displays visualizations, retrieves data, and responds to user interactions.

Q2. What is Tableau Performance Recording?

Answer: It is a diagnostic feature that records information about workbook events so developers can identify time-consuming operations.

Q3. How do you start Performance Recording in Tableau Desktop?

Answer: Open Help, select Settings and Performance, and choose Start Performance Recording. Reproduce the issue and select Stop Performance Recording to review the generated workbook.

Q4. What is the difference between query execution and query compilation?

Answer: Query compilation concerns generating or compiling queries, while query execution concerns running the query to retrieve or process data.

Q5. What can cause slow dashboard rendering?

Answer: Large numbers of marks, complex visualizations, excessive labels, and complicated dashboard layouts can increase rendering time.

Q6. How can you improve a dashboard with too many worksheets?

Answer: Remove redundant sheets, focus the dashboard on its main business questions, and move detailed analysis to supporting views when appropriate.

Q7. How can filters affect performance?

Answer: Filters can trigger queries and recalculations. Too many filters or high-cardinality controls can increase interaction time.

Q8. What is the difference between a live connection and an extract?

Answer: A live connection queries the connected source, while an extract uses a stored data snapshot that must be refreshed to include newer data.

Q9. Why might a dashboard work well in Desktop but slowly after publishing?

Answer: Server capacity, concurrent users, network latency, data source access, authentication, and deployment configuration can affect published performance.

Q10. How can you diagnose a slow database query?

Answer: Identify the query event in Performance Recording, inspect the available query details, and use database diagnostic tools or the database team's assistance to investigate execution time.

Q11. What is Workbook Optimizer?

Answer: It is a Tableau feature that evaluates workbook design choices against performance best practices and provides recommendations where supported.

Q12. Why should you make one optimization change at a time?

Answer: Controlled changes make it easier to determine which modification caused a performance improvement or regression.

Q13. Does using an extract always improve performance?

Answer: No. Extracts can help in suitable scenarios, but performance depends on data volume, query patterns, source behavior, refresh requirements, and workbook design.

Q14. How can too many marks affect a dashboard?

Answer: Too many marks can increase rendering and interaction costs. Appropriate aggregation and guided drill-down can reduce unnecessary detail.

Q15. What should be checked after optimizing a dashboard?

Answer: Recheck load time, filter response, query and rendering behavior, numerical accuracy, data freshness, and performance in the published environment.

26. Practical Exercises

1. Create a dashboard with at least four worksheets and measure its baseline loading time.
2. Use Performance Recording to identify the longest-running events.
3. Remove one unnecessary worksheet and compare the results.
4. Create a dashboard with several filters and investigate their effect on interaction time.
5. Compare a live connection with an extract when suitable test data is available.
6. Build a view containing many marks and compare it with an aggregated view.
7. Inspect a calculated field used by a slow worksheet and simplify it where possible.
8. Test a dashboard in Desktop and in the intended published environment.
9. Create a before-and-after report documenting at least three measured changes.
10. Verify that all sales, profit, and record-count metrics remain accurate after optimization.

27. Dashboard Performance Checklist

• Have you reproduced and measured the performance issue?
• Have you used Performance Recording to identify the longest events?
• Have you determined whether the delay is caused by queries, calculations, connections, layout, or rendering?
• Have you removed unnecessary worksheets and dashboard objects?
• Have you reduced unnecessary marks and labels?
• Have you reviewed expensive calculations and custom SQL?
• Have you checked data model relationships and join behavior?
• Have you reviewed filter count, filter scope, and dashboard actions?
• Have you evaluated live connections and extracts based on business needs?
• Have you tested with realistic data volumes?
• Have you compared performance before and after the changes?
• Have you verified that all business metrics remain accurate?
• Have you tested the published dashboard?
• Have you documented the results and remaining limitations?

28. Official Tableau Learning Resources

• Optimize Workbook Performance — learn about performance considerations for data, connections, calculations, and workbook design.
• Record and Analyse Workbook Performance — learn how to record performance and interpret the resulting workbook.
• Tableau Workbook Performance Checklist — review practical optimization recommendations.
• Improve Dashboard Performance with Design Best Practices — explore performance recording, workbook optimization, and dashboard design guidance.
• Interpret a Performance Recording — understand performance recording results in a Tableau Server context.

29. Quick Revision

30. Conclusion

Diagnosing dashboard performance problems in Tableau requires a structured approach. Begin by reproducing the issue and measuring its impact. Use Performance Recording to identify whether the bottleneck is related to query execution, query compilation, data source connections, layout, or rendering. Then apply targeted improvements to the relevant data source, calculations, filters, worksheets, or dashboard design.

The most effective optimization strategy is based on evidence rather than guesswork. Test changes individually, compare before-and-after performance, validate business calculations, and verify the published dashboard in its actual environment. These practices help produce Tableau dashboards that are responsive, reliable, and easier to maintain.

Explore Tableau Training: JustAcademy Tableau Training

Register for a Tableau Course Demo: Register for a Tableau Course Demo